Skip to content

fix: move minimum-release-age to pnpm-workspace.yaml, fix Socket package downgrades#136

Merged
John-David Dalton (jdalton) merged 2 commits intomainfrom
fix/minimum-release-age
Apr 4, 2026
Merged

fix: move minimum-release-age to pnpm-workspace.yaml, fix Socket package downgrades#136
John-David Dalton (jdalton) merged 2 commits intomainfrom
fix/minimum-release-age

Conversation

@jdalton
Copy link
Copy Markdown
Collaborator

Summary

  • Move minimum-release-age from .npmrc to pnpm-workspace.yaml (minimumReleaseAge) to avoid npm v11+ Unknown project config warning
  • Fix update script: pnpm update @socketsecurity/* --latest was downgrading packages younger than 7 days. Now bypasses age gate via npm_config_minimum_release_age=0 env for Socket packages

Test plan

  • pnpm run update no longer downgrades Socket packages
  • pnpm config list shows minimumReleaseAge=10080 from workspace

…age downgrades

- Move pnpm's minimum-release-age from .npmrc to pnpm-workspace.yaml
  to avoid npm v11+ warning about unknown config key
- Keep min-release-age=7 in .npmrc for npm
- Fix update script: bypass age gate for @socketsecurity/* and
  @socketregistry/* via env override (prevents downgrades)
…ion test

The two clock-skew tests didn't actually test clock skew — they just did
set/get/clear without creating far-future entries. They were slow
(filesystem IO) and caused CI worker timeouts. Replaced with a single
memoized TTL expiration test that verifies entries expire after TTL.
@jdalton John-David Dalton (jdalton) merged commit 0145a82 into main Apr 4, 2026
12 checks passed
@jdalton John-David Dalton (jdalton) deleted the fix/minimum-release-age branch April 4, 2026 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant